Small addition: This will also fix #1688 as it's caused by the same default values. I think we should still consider removing size as a DTO field for Dataset, since it's mostly managed/updated by the backend when changing OrigDatablocks.

@HayenNico should I bring it up in the collaboration meeting and ask opinion there?

That said, I think that this field is important given that one dataset can have multiple origDatablock and multiple files associated with it

@nitrosx I did not mean to remove size from Dataset schema, only the DTOs. In the code, when an OrigDatablock is created/updated, the size of the associated Dataset is also recalculated. As such, I'd call that a field that's managed by the backend, and it should not be available to edit in the Dataset DTO itself.
Right now, one could in principle overwrite size in a Dataset via the API, such that it does not have any relation to the data files anymore. See also #1688 for more details

@nitrosx I did not mean to remove size from Dataset schema, only the DTOs. In the code, when an OrigDatablock is created/updated, the size of the associated Dataset is also recalculated. As such, I'd call that a field that's managed by the backend, and it should not be available to edit in the Dataset DTO itself. Right now, one could in principle overwrite size in a Dataset via the API, such that it does not have any relation to the data files anymore. See also #1688 for more details

Yes I agree with this. I think as we are calculating this on the backend side it is a good idea to remove it from the update and create DTOs and just leave it in the database schema. This removes the possibility to update those fields by mistake and have the backend calculations as the only source of truth when it comes to total size and number of files. I am not sure if I should do that as part of this PR or it can be done separately in another one. @nitrosx let me know what do you think

Remove size from the create and update DTO and manage it internally.
It should stay in the output DTO.

I would say create an additional PR